Range count and main memory address accounting system

ABSTRACT

In a peripheral controller of a data processing system having a plurality of system units electrically coupled to a common communication bus for asynchronous intercommunication, an array of counters responsive to both hardware and firmware are connected in a manner to form a serial control data path. Prior to a data transfer, a serial data stream including an offset range count, a range count and a main memory address is shifted through the counters under firmware control. During a data transfer, the firmware enables the hardware control to increment the memory address and decrement the range count to accommodate the higher data transfer rates characteristic of hardware control.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to an accounting means for tracking the flow ofdata between a peripheral storage device and main memory, and moreparticularly a data byte accounting system combining the economy andreliability of firmware with the high data transfer rates characteristicof hardware control.

2. Prior Art

Data processing systems wherein a plurality of system units areelectrically coupled to a common communication bus for asynchronousintercommunication are disclosed in U.S. Pat. No. 3,993,981 and in U.S.application Ser. No. 643,439 filed Dec. 22, 1975, now U.S. Pat. No.4,003,033 each assigned to the assignee of the present invention.

Prior data processing systems having the common bus architecture haverelied solely on firmware control to accommodate data transfers betweenmass storage devices such as a disk and the common bus. With theincorporation of mass storage devices supplying data words at a rate ofthe order of ten times that of the prior transfer rates, a new controlarchitecture was required. Further, the time penalties suffered inamending range counts and memory address data directly from a scratchpadmemory could no longer be tolerated. Thus, the system data ratesrequired a departure from the previous all firmware controlarchitecture.

The present invention is directed to a system wherein system datacontrol is shared between firmware and hardware in a manner toaccommodate high data transfer rates.

SUMMARY OF THE INVENTION

An accounting system architecture responsive to both firmware andhardware control is provided for dynamically tracking data bytetransfers.

More particularly, address counters, range counters and offset rangecounters are connected in a manner to form a serial data path, therebyaccommodating a data load with minimal firmware interaction. A memoryaddress, a range count and an offset range count are loaded fromscratchpad memory under firmware control prior to a data transfer. Thefirmware control thereafter enables the hardware control to incrementthe address counters and decrement the range counters during the datatransfer to accommodate a data transfer rate higher than that possibleunder firmware control.

DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and forfurther objects and advantages thereof, references may now be had to thefollowing description taken in conjunction with the accompanyingdrawings in which:

FIG. 1 is a functional block diagram of a data processing system havingsystem units electrically coupled to a common communication bus;

FIG. 2 is a functional block diagram of the disk controller of FIG. 1;

FIGS. 3A and 3B are graphical illustrations of communication wordstransferred through the common bus of FIG. 1;

FIGS. 4 and 5 are a detailed functional block diagram of the diskcontroller of FIG. 1;

FIG. 6 is a functional block diagram of a firmware control system usedin controlling the operation of the system of FIGS. 4 and 5;

FIGS. 7A and 7B are detailed functional block diagrams of the range andoffset range control unit of FIGS. 4 and 5;

FIG. 8 is a detailed logic diagram of the data FIFO unit of FIG. 4;

FIG. 9 is a timing diagram of the operation of the system of FIG. 8;

FIG. 10 is a timing diagram of the operation of the system of FIGS. 4-8during a data transfer from a disk device to the common communicationbus; and

FIG. 11 is a timing diagram of the operation of the system of FIGS. 4-8during a data transfer from the main memory unit to the disk adapter ofFIG. 1.

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1

FIG. 1 illustrates in functional block diagram form a computer systemhaving a medium-performance disk controller (MPDC) 10 in electricalcommunication with a central processor unit 11 and a main memory unit 12by way of a common communication bus hereinafter referred to as megabus13. The MPDC 10 is a microprogrammed peripheral control subsystem forstoring and retrieving data from mass storage media. The controllerincludes a Read Only Store (ROS) memory to be later described havingstored therein microprogram instructions. The ROS communicates with massstorage adapters such as the device adapter 14, which has the facilityto support plural daisy-chained disk devices 15.

The megabus 13 provides an information path between any two units in thesystem. The paths are asynchronous in design, thereby enabling units ofvarious speeds to operate efficiently. The bus accommodates informationtransfers including communication requests, control commands, statussignals and data transfers between main memory 12 and disk devices 15.

Any system unit requiring communication with any other system unitissues a bus cycle request. When the bus cycle is granted, therequesting unit becomes the master and the addressed system unit becomesthe slave. Some bus interchanges require a response cycle as well as arequest cycle. By way of example, the master unit may identify itself toa slave unit and indicate that a response is required. When the requiredinformation becomes available, the slave assumes the role of master andinitiates a transfer to the requesting unit.

In the servicing of bus cycle requests, the central processor has thelowest priority, the MPDC 10 has the next to the lowest priority, andthe memory 12 has the highest priority.

A more detailed background description of the system of FIG. 1 is givenin U.S. Pat. No. 3,993,981 which is assigned to the assignee of thepresent invention, and which is incorporated by reference herein.

FIGS. 2 AND 3

FIG. 2 illustrates in functional block diagram form the MPDC 10 of FIG.1, and FIG. 3 graphically illustrates the binary instruction formatsnecessary for the operation of the MPDC.

The megabus 13 is connected to an address logic unit 20 by way of anaddress cable 21. Logic unit 20 is comprised of address transceiversthrough which memory addresses, channel destination numbers and functioncodes are transferred between the MPDC 10 and the megabus 13. The logicunit 20 further is comprised of control logic for distributinginformation on the address cable 21 throughout the MPDC.

Logic unit 20 is connected to a range and offset range logic unit 22 byway of a unidirectional control cable 23, and connected to an arithmeticlogic unit 24 by way of a bidirectional control cable 25. The logic unit22 includes a 16-bit range counter which is loaded with the number ofbytes to be transferred during a read or write operation. The logic unitfurther includes a 16-bit offset range counter which is loaded with acount indicating the number of leading data bytes to be ignored during aread data transfer.

The arithmetic logic unit (ALU) 24 is the focal point of all dataoperations within the MPDC. Such data operations may occur between MPDC10 and the megabus 13, or between the MPDC and the device adapter 14.The ALU performs both logic and arithmetic operations on incoming data,and is comprised of an A-operand multiplexer (AMUX), a B-operandmultiplexer (BMUX), and eight-bit arithmetic unit (AU), and an eight-bitaccumulator (ACU) to be further described. Under firmware control, theAMUX selects one of eight data fields and the BMUX selects one of fourdata fields. The AU performs 8-bit arithmetical and logical operationson the data selected by the multiplexers, and supplies the result to theaccumulator for temporary storage.

The ALU receives range and offset range control signals from the logicunit 22 by way of a control cable 26, and firmware control signals froma microprogram control store logic unit 27 by way of a control cable 28.The ALU 24 further communicates with an adapter logic unit 29 by way ofa bidirectional control cable 30, and with a scratchpad memory unit 31by way of a bidirectional control cable 32. In addition, the ALU 24communicates with the device adapter 14 by way of a bidirectionalcontrol cable 33, and supplies control information to a bus logic unit34 by way of a unidirectional control cable 35. The ALU also receivesand transfers data to a data logic unit 36 by way of a bidirectionaldata cable 37.

The adapter logic unit 29 is connected to the device adapter 14 by wayof a bidirectional communication cable 38. The logic unit 29 providesthe MPDC with a communication path to control the transfer of data andstatus information between the adapter 14 and the MPDC 10.

The scratchpad memory unit 31 includes logic comprised of an indexregister, an address register, an address selector, a scratchpad memory,and the logic elements controlling the operation of the scratchpadmemory. The scratchpad memory is a 1.024K-bit by 8-bit read/write memorywhich is segmented into indexed and non-indexed sections, each sectioncontaining two quadrants. The non-indexed section of the memory iscomprised of 256 work locations and 256 reserve locations. The indexedsection of the memory is comprised of 256 locations for the storage ofdevice-related information and 256 reserve locations. The 256 locationsfor device-related information are further subdivided into foursections, each comprising 64 locations per channel.

The address register of the scratchpad memory unit 31 is a 10-bitregister, wherein the high order bit selects either the indexed ornon-indexed mode. The second high order bit selects a 256-locationquadrant, and the next two bits select 64 locations within the quadrant.The six low order bits select a scratchpad address. Data is written intothe selected address of the scratchpad memory unit from the AMUX of theALU 24 during the execution of a firmware memory write command. The dataout of the scratchpad memory is delivered to the AMUX and the BMUX fordistribution throughout the MPDC.

The microprogram control store logic unit 27 is typical of that known inthe art, and includes a return register unit, a selector, a microprogramaddress counter, a Read Only Store (ROS) memory, a microprograminstruction register (MPIR), a decoder and a firmware distribution unitto be further described. The ROS provides permanent storage for residentcontrol firmware and diagnostic microprograms, and may be addressed toselect various microinstruction sequences for execution. The ROSprovides a 16-bit wide output derived from the outputs of sixteen 1,024by 4-bit programmable Read Only Memory (PROM) chips. The ROS output isapplied to the MPIR which is a 16-bit wide register used to store theoutput of the ROS for one clock cycle during a microinstructionexecution.

The bus logic unit 34 receives control signals from the ALU 24 by way ofcable 35, and from the microprogram control store logic unit 27 by wayof cable 28 and a control cable 39. The logic unit 34 is connected tothe megabus 13 by way of a bidirectional control cable 40. The bus logicunit 34 performs asynchronous handshaking operations by responding toand generating megabus cycle requests. Further, simultaneous requestsand grants of megabus cycles are accommodated on a priority basis withthe MPDC at an intermediary priority position and the main memory at aposition of increased priority.

The data logic unit 36 includes error checkers, five 16 word by 4-bytefirst-in-first-out (FIFO) data buffers and a read selector foraccommodating the transfer of data or a bidirectional data cable 41between the MPDC 10 and the megabus 13. Any information entering theMPDC 10 from the megabus 13 is gated through data transceivers andchecked for parity. The same logic is used to deliver the MPDC channelnumber to the megabus 13 in response to a bus cycle request from asystem unit. Four of the five FIFOs receive data, and the fifth FIFO isused to prevent the MPDC from making a cycle request when the data FIFOsare full. The FIFO chips are capable of stacking 14 words, plusretaining one word in the input and output registers to provide a totalcapacity of 16 words.

Clock signals for controlling the operation of the MPDC 10 are providedby a system clock unit 42 comprised of an 8 MHz crystal oscillator. Thesystem clock signal is applied to a clock logic 43 which provides a 4MHz square wave that is distributed throughout the MPDC. The clock logicunit 43 also receives control signals from the microprogram controlstore logic unit 27 by way of a control line 44 to enable or reset thelogic unit.

The operations performed by the MPDC 10 include a direct memory access(DMA) read, a DMA write, an I/O output command, an I/O input command andan interrupt operation. Each of the operations require a single buscycle except for the DMA read and the I/O input commands which requiretwo bus cycles.

Referring to FIGS. 3a and 3b, the specific parameter formats for machineinstructions used in megabus communications with the MPDC areillustrated. When a data transfer is to occur, the CPU 11 of FIG. 1issues a machine instruction referred to as an I/O Output Command whichincludes a destination channel number, a 6-bit function code, and a dataword as illustrated by the I/O output command format of FIG. 3a. Thedestination channel number identifies the system device to which arequest is directed, and the function code provides the address inscratchpad memory unit 31 to which a data transfer is directed. Thefunction code further identifies a CPU command as an input or an outputcommand. The data word may include a task to be executed, range andoffset range counts, a main memory address, or configuration words usedto control the disk device during a data transfer. As shown in FIG. 3a,the destination channel numbers and function codes are transferredbetween the megabus 13 and the MPDC 10 by way of the address logic unit20. The source channel number, main memory addresses, range and offsetrange and information stored in reserve areas are transferred betweenthe megabus and the MPDC by way of the data logic unit 36. If data is tobe written into main memory 12 of FIG. 1, the CPU 11 issues a DMA memorywrite operation. In response thereto, the starting memory address 60a isapplied to the megabus 13 via the address cable 21, and the data 60b tobe written into memory is applied to the megabus via the cable 41. Asillustrated in FIG. 3a, the memory address register is a 24-bitregister, while the data register is a 16-bit register.

If data is to be read from main memory 12, the CPU 11 issues a machineinstruction referred to as a DMA memory read request. The instructionincludes a 24-bit memory address 61a, a 10-bit source channel number61b, and a 6-bit reserve area 61c. The memory address 61a is receivedfrom the megabus 13 via cable 21 leading to the address logic unit 20.The channel number 61b and reserve area 61c are received by the datalogic unit 36 by way of data cable 41. In response to the DMA readrequest instruction, the MPDC issues a DMA memory read responseinstruction comprising a 10-bit destination channel number 62a, a 6-bitreserve area 62b, and 16 bits of data 62c to be transferred. Thedestination channel number and reserve area are transferred to themegabus by way of the address cable 21, while the 16 bits of data aretransferred to the megabus by way of data cable 41. It is to beunderstood that the contents of the reserve area 62b is identical tothat of the reserve area 61c. Thus, information stored by the CPU intothe reserve area 61c is returned to the megabus by way of the reservearea 62b.

The CPU 11 may transfer data from main memory and indicate a task whichthe MPDC 10 is to perform upon the data. For example, the CPU may issuean I/O output command instruction comprising a 10-bit destinationchannel number 63a to identify the MPDC, a 6-bit function code 63b toidentify a scratchpad memory address, and 16 bits of data 63c to bestored in the indicated scratchpad location. As before described, thedestination channel number and function code are received by the addresslogic unit 20 by way of address cable 21, and the data is stored in thedata logic unit 36. The data is transferred under firmware control fromthe logic unit 36 to the ALU 24, and thereafter stored in the scratchpadmemory unit 31. The CPU 11 issues additional I/O output commands tostore into the scratchpad a range, an offset range, a main memoryaddress, a task to be executed and configuration words for controllingthe operation of the disk device during a data transfer. The firmwarefurther may determine from the low order bit of the function codewhether the task includes an input or an output operation. The task mayinclude any of the beforedescribed MPDC operations.

If the CPU 11 requires information from the MPDC 10, an I/O inputcommand instruction may be issued. The instruction is comprised of a10-bit destination channel number 64a, a 6-bit function code 64b, a10-bit source channel number 64c identifying the source of the request,and a 6-bit reserve area 64d. In response to the CPU request, the MPDCissues an I/O input response instruction comprising a 10-bit destinationchannel number 65a, a 6-bit reserve area 65b having stored therein thedata appearing in reserve area 64d, and 16 bits of data 65c.

When data is to be written into the scratchpad memory unit 31, a twocycle operation occurs. The CPU 11 issues an I/O load output commandwhich is comprised of two instructions. The first instruction includesan 8-bit module number 66a indicating the high order eight bits of amain memory address, a 10-bit destination channel number 66b, a 6-bitfunction code 66c, and 16 address bits 66d indicating the low order bitsof a 24-bit main memory address. The module number, destination channelnumber and function code are transferred through address logic unit 20and ALU 24 to the scratchpad memory unit 31 under firmware control. Thefirmware thereafter accesses the function code in the scratchpad memoryto identify the scratchpad memory address into which the main memoryaddress data is to be written. Upon loading the address in thescratchpad memory, the firmware commands the bus logic unit 34 to issuea ready signal to the megabus 13. The CPU in response thereto issues asecond instruction including a 10-bit destination channel number 67adesignating the MPDC, a 6-bit function code 67b, a high order bit 67cindicating whether the range count is positive or negative, and 15 rangebits 67d indicating the number of data bytes to be transferred. Thefirmware thereupon accesses the function code to determine thescratchpad memory locations into which the range and S bit are to bestored.

In an interrupt operation, the MPDC issues an interrupt instructioncomprising a 10-bit destination channel number 68a, a 6-bit logic zeroarea 68b, a 10-bit source channel number 68c, and a 6-bit sourcepriority level number 68d. When the MPDC completes an operation, theinterrupt instruction is issued to the CPU 11. If the priority levelnumber of the MPDC is higher than the priority level of the task that iscurrently being performed by the CPU, the MPDC interrupt will beserviced immediately. Otherwise, the MPDC enters a wait state until aCPU is received.

The formats of two configuration words used to control the operation ofa disk during a data transfer are illustrated in FIG. 3b. Theconfiguration words A and B include an image of an ID field of a disksector on which a particular operation will be initiated. Moreparticularly, the configuration word B includes a 7-bit area reservedfor user (RFU) 69a, a 1-bit track number 69b and an 8-bit sector number69c. The sector number field is incremented by one after each data fieldis successfully transferred during a read or a write operation.

Configuration word A includes a 4-bit RFU field 70a, a 1-bit platterselect field 70b, a 2-bit RFU field 70c, and a 9-bit cylinder numberfield 70d. The cylinder number and platter select fields are used as theseek arguments for disk seek operations.

The operation of the invention may best be described in the context of aread or a write operation. If the firmware on evaluating a task word inmemory unit 31 detects a command for writing a record onto a disk, thefirmware accesses the configuration words A and B in memory unit 31 byway of the ALU 24. The firmware thereafter stores the words in thedevice adapter 14, which compares the words with track information readfrom the disk. During the period that the logic unit 29 is searching foran ID match, the firmware commands the bus logic unit 34 to request datafrom the main memory unit 12. In response thereto, the main memorytransfers 32 bytes of data to the FIFOs of the data logic unit 36. Asthe data is being loaded into the data logic unit, the range count inlogic unit 22 is decremented and the address logic unit is incremented.

When an ID match occurs, the adapter 14 initiates a write gap operationon the indicated record of the disk system. Sixteen of the 32 bytes ofdata in the data logic unit 36 thereupon are moved from the data logicunit 36 to the device adapter 14 by way of ALU 24. As the data is beingtransferred to the adapter 14, the firmware commands the bus logic unit34 to request additional data from the memory unit 12. Theabove-described process continues until the range field of the logicunit 22 is exhausted.

If data is to be read from a disk device and written into main memory12, the CPU 11 first issues machine instructions for storingconfiguration words A and B, range, offset range, a beginning mainmemory address and a task to be performed into the scratchpad memory. Inresponse to firmware initiated control signals from the adapter logicunit 29, the device adapter 14 searches a disk device to find the datarecord to be transferred. When the disk track has been identified asbefore described, the data is transferred under hardware control to thedata logic unit 36 by way of cable 33 and ALU 24. The hardware accessesthe offset range count of the logic unit 22 to detect the number ofleading data bytes to be ignored. The logic unit 36 thereafter forms2-byte words from the succeeding data, and transfers a word underhardware control to the megabus 13 each time two bytes are received. Thedata transfer continues from the disk adapter 14 to the data logic unit36 until the range register of the address logic unit 20 indicates thatthe data transfer is complete.

FIGS. 4 AND 5

FIGS. 4 and 5 illustrate in a more detailed functional block diagramform the system of FIG. 2.

A 24-bit address shift register 70 is connected to the megabus 13 by wayof a 24-bit data cable 71. The output of the shift register is appliedto the A2 input of an 8 to 1 multiplexer 72 (AMUX). Bits 15 and 16 ofthe shift register output are applied by way of a data cable 73 to thetwo-bit A1 input of an index register 74. The clock (CK) input to shiftregister 70 is connected to a control line 70a leading to a firmwareoutput terminal to be further described.

The A1 input to AMUX 72 is connected to the 8-bit output of anaccumulator 75, and the A3 input to AMUX 72 is connected by way of adata cable 76 to the output of a range and offset range control unit 77to be later described. The A4 input to AMUX 72 is connected by way of adata cable 78 to an output of an 8-bit scratchpad address counter 79.The A5 input to AMUX 72 is connected to a data cable 80 leading from theD1 two-bit output of index register 74, and the A6 input to AMUX 72 isconnected to the 8-bit output of a 1K by 8-bit scratchpad memory 81. TheA7 input to AMUX 72 is connected to the output of a 16-bit data register82. The select (SEL) input to the AMUX 72 is connected by way of acontrol line 72a to a firmware output terminal. The 8-bit output of AMUX72 is connected to the A1 input of an OR logic unit 83.

A 4-to-1 multiplexer 84 (BMUX) has an 8-bit output connected to the A2input of an arithmetic unit 85. The A1 input to BMUX 84 is supplied byfirmware on a control cable 86. The A2 input to BMUX 84 is connected tothe output of scratchpad memory unit 81 by way of a data cable 87. TheA3 input to BMUX 84 is supplied by way of a control cable 88, and the A4input to the multiplexer is connected to the output of the accumulator75 by way of a data cable 89. The select (SEL) input to the multiplexeris supplied by firmware on a control line 84a.

The A1 input to arithmetic unit 85 is connected by way of a data cable90 to the 8-bit D1 output of logic unit 83, and the mode input to thearithmetic unit is connected to the output of an arithmetic control unit91. The 8-bit output of the arithmetic unit is applied to the input ofaccumulator 75, and applied by way of data cables 92 and 93 to the datainput of counter 79. Further, the output of the arithmetic unit isapplied by way of data cables 92 and 94 to the A2 input of deviceadapter 14, and by way of data cable 95 to a data cable 96. Thearithmetic unit output also is applied by way of data cables 95 and 97to the input of a second half-read (SHRD) register 98, and by way ofdata cables 95 and 99 to the 8 bit data inputs of a 16-bit bus dataregister 100. The arithmetic unit output in addition is applied to datacables 95 and 101 leading to the data input of a test logic unit 102.

The output of accumulator 75 further is applied to a data cable 103, andto the two bit A2 input of index register 74. The load (LD) input to theaccumulator is connected by way of a control line 75a to a firmwareoutput terminal.

The A1 input of arithmetic control unit 91 is connected by way of acontrol line 106 to an output terminal of the firmware control system,and the A2 input to the control unit 91 is connected by way of a controlline 107 to the D1 output of a hardware control unit 108.

The A1 input to control unit 108 is connected to a control line 109leading to an output of the firmware control system, and the A2 input tothe control unit 108 is connected to a control line 108a. The A3interrupt input of control unit 108 is supplied by the device adapter 14to a control line 110. The A4 input to the control unit is connected toa control line 108b leading from system hardware control. The D2 outputof control unit 108 is connected by way of a control line 111 to the A1input of adapter logic unit 29, and the D3 output of the control unit108 is connected to a control line 112 leading to the A1 input of a datacontrol unit 113. The D4 output of control unit 108 is connected by wayof a control line 70b to the load (LD) input of shift register 70, andthe D5 output is connected to the A1 input of test logic unit 102. TheD6 output of the control unit is connected to a control line 108cleading to the system hardware control.

Firmware generated clock signals on a control line 79b are supplied tothe clock (CK) input of address counter 79, and firmware control signalson a control line 114 are supplied to the LD input of the counter.Further, the up/down select input to the counter receives firmwarecontrol signals by way of a control line 79b. Two output bits of thecounter are applied to the A1 input of a selector 115. The low order sixbits of the counter output are applied to the A2 input of the scratchpadmemory unit 81.

The A2 input of selector 115 is connected to the D2 output of indexregister 74, the LD input of which is supplied by firmware to a controlline 74a. The 3 bit output of the selector 115 is applied to the address(ADDR) input of scratchpad memory unit 81, and the SEL input of theselector receives firmware control signals by way of a control line 116.

The A1 input to memory unit 81 is connected by way of a data cable 117to the 8 bit D2 output of logic unit 83. The A2 input to logic unit 83is connected to the D1 output of data FIFO unit 118, and the A3 input tologic unit 83 is connected to the D2 output of unit 118. The A4 input tologic unit 83 is supplied by the device adapter 114 by way of a datacable 119.

The data input to the data register 82 is connected to a 16 bit datacable 120 electrically connected to the megabus 13, and the output ofthe data register further is connected to the input of the data FIFOunit 118. The LD input to the register is supplied by hardware controlon a control line 82a. The output of the register further is applied todata cables 139 and 140.

The LD input to data register 100 is supplied by data control unit 113on a control line 121. The output of register 100 is applied to the A2input of a 2-to-1 data multiplexer 122. The 16 bit A1 input to themultiplexer is supplied by the SHRD register 98, the LD input of whichis supplied by data control unit 113 on a control line 98a. The outputof the multiplexer is applied by way of a 16 bit data cable 123 to themegabus 13.

Referring to test logic unit 102, a status signal is applied to the A2input of the logic unit by the firmware control system on a control line124. In addition, the bus logic unit 128 supplies a status signal by wayof a control line 102a to the A3 input of the logic unit 102, and thecontrol unit 77 supplies an end of range signal to the A4 input of thelogic unit by way of a control line 102b. The A5 input of logic unit 102is connected to a control line 125 carrying interrupt signals from theD1 output of device adapter 14. The test logic unit supplies a controlsignal to a control line 126 leading to a firware control system to befurther described.

The adapter logic unit 29 also receives a firmware signal on a controlline 127 connected to its A2 input. The output of the logic unit isapplied to the A1 input of device adapter 14. A control line 29a leadingfrom the output of the logic unit is connected to the A5 input of datacontrol unit 113, and to a control line 118b leading to the transfer onparallel (TOP) input of Data FIFO unit 118.

As illustrated by FIG. 5, the megabus 13 is connected to bus logic unit128 by way of a bidirectional data cable 129. The A2 input of logic unit128 is connected to data cable 103 carrying the output of accumulator75, and the A3 input to the logic unit is connected to a control line130 leading to an output of the firmware control system. The A4 input tologic unit 128 is connected to the D1 output of control unit 77, and theA5 input to the logic unit is connected to the D1 output of afirst-in-first-out (FIFO) unit 131. The A6 input to the logic unit issupplied by system hardware on a control line 128a. The D1 output oflogic unit 128 is connected to data cable 88, and the D2 output isconnected to a control line 132 leading to the select (SEL) input ofdata multiplexer 122. The D3 output of the logic unit is connected tothe A2 input of data control unit 133, and the D4 output is connected tothe A1 output of FIFO unit 131. The D5 output of logic unit 128 isconnected to the SEL input of a dual 2-to-1 address multiplexer 133, andthe D6 output of the logic unit is connected to control line 102a.

The A2 input to FIFO unit 131 is connected to the D1 output of controlunit 113, and the D2 output of the FIFO unit is connected to the A3input of control unit 113. The A4 input to control unit 113 is connectedto an output of the firmware control system by way of a control line134, and the A5 input of the control unit is connected to line 29a. TheD2 output of the control unit is connected to control line 121, and theD3 output is applied by way of a control line 135 to a control (CTR)input of data FIFO unit 118. The D4 output of data control unit 113 isapplied to the A1 input of control unit 77, and the D5 output is appliedto control line 98a leading to the LD input of register unit 98.

The A2 input to control unit 77 is connected to the D1 output of a busaddress register unit 136, and the A3 input to the control unit isconnected by way of a control line 137 to an output of the firmwarecontrol system. The D2 output of the control unit 77 is applied to datacable 76 leading to an input of AMUX 72. The D3 output of control unit77 is applied to a control line 77a leading to the A3 input of deviceadapter 14, and to control line 102b leading to the A4 input of testlogic unit 102 as before described.

The bus address register unit 136 is comprised of a 24-bit up counterwhich may be controlled to count either bytes or words, where a word iscomprised of two bytes. The 8-bit D1 output of unit 136 also is appliedto the B1 input of address multiplexer 133, and the 8-bit D2 output ofthe unit 136 is applied to the B2 input of multiplexer 133. The 8-bit D3output of unit 136 is applied by way of a data cable 138 to the megabus13. The LD input to the register unit 136 is supplied by firmware on acontrol line 136a. The 8-bit A1 and A2 inputs to address multiplexer 133are supplied by data register 82 by way of data cables 139 and 140.

In operation, the MPDC 10 interfaces with the disk adapter 14 which inturn may service plural disk devices as illustrated in FIG. 1.

If an unsolicited bus request is received from the megabus 13, the buslogic unit 128 issues a signal on line 102a leading to the test logicunit 102. Further, a device adapter 14 request is indicated by aninterrupt signal on control line 127. The logic unit thereby is notifiedwhether a device adapter request or a megabus 13 request is to beserviced. The test logic unit 102 thereupon indicates to the firmware byway of a signal on control line 125 the microinstruction sequence to beexecuted. In the event that a request is directed to a disk device whichis already involved in executing a task, the bus logic unit 128 willissue a not accepted (NAK) status signal to the megabus 13 under systemhardware control. If a disk device not presently involved in executing atask is addressed by the megabus 13, but the MPDC is presently involvedin executing a previous task involving a second disk device, then thelogic unit 128 may issue a wait status signal to the megabus 13. If thedisk device which is addressed is not busy, and the MPDC is not involvedin servicing the device while executing a previous task, then an accept(ACK) status signal is issued to the megabus 13.

It is to be understood that in the operation of the MPDC, the data pathsfor a data transfer are prepared by firmware operating in combinationwith the system of FIGS. 4 and 5. The data transfer, however, occursunder system hardware firmware control. Detailed descriptions of suchhardware may be found in U.S. Pat. No. 3,993,981, and in the followingHoneywell reference manuals: MPDC Reference Manual, Doc. No.71010241-100, Order No. FM55, Rev. 0; MPDC Cartridge Disc AdapterReference Manual, Doc. No. 71010239-100, Order No. FM57, Rev. 0; andMPDC Disc Adapter Reference Manual, Doc. No. 71010441-100, Order No.FK90, Rev. 0.

In a read or a write operation, the CPU 11 of FIG. 1 initially suppliesa channel destination number and a function code to the address shiftregister 70. The shift register is compared under system hardwarecontrol to a destination number set in hex rotary switches, and if amatch is detected the bus logic unit 128 acknowledges the match to thebus 13. As before described, the acknowledgement may be a wait, anonacceptance (NAK), or an acceptance (ACK). If an ACK acknowledgementis issued by the logic unit 128 to the megabus 13, the logic unit inaddition issues a busy signal to the megabus 13 to place subsequent busrequests in a wait state. The system hardware thereafter controls thetransfer of data between megabus 13 and MPDC 10.

In order to provide means for controlling the operation of the diskdevice during a read or a write operation, the CPU 11 also supplies aconfiguration word A to megabus 13 which under hardware control isloaded into the data register 82 and address shift register 70. Uponcompleting the load operation, the system hardware issues an ACK signalto the megabus 13 followed by a busy signal. Firmware senses the busysignal, and controls the transfer of the data in address shift register70 and data register 82 through the arithmetic unit 85 for storage intoscratchpad memory 81. When the firmware has completed the memory storeoperation, it signals the system hardware which then controls theloading of the address and data registers with a configuration word B.The configuration word B then is loaded into scratchpad memory underfirmware control, and the process is repeated to receive in order a mainmemory address, a range count, a task and a status request. When thetask is loaded into the data register 82 and stored in scratchpad memory81, the task is executed under firmware control. Upon completing thetask, the function code is interrogated to detect the presence of statusrequests which may be honored.

In the memory store operation, the firmware senses the function code todetermine the scratchpad address in which information is to be storedfrom data register 82. Further, firmware is able to distinguish betweendata formats by interrogating the function code. A function code of hex0 7 indicates that a task has been loaded into the scratchpad memory, afunction code of hex 1 1 identifies a configuration word A and afunction code of hex 1 3 identifies a configuration word B. In addition,a function code of hex O D identifies a range count (data bytes to betransferred). It is to be noted that the configuration words A and B,the task, and the range have formats as illustrated by the data field ofI/O output command word of FIG. 3a. A main memory address input,however, is comprised of the module number and address fieldsillustrated by the I/O LD output command word of FIG. 3a.

During a read operation wherein data is read from a disk device andstored in main memory unit 12, the system hardware loads the high orderbits of a main memory address, a function code and a channel destinationnumber from megabus 13 into the address shift register 70, and loads thelow order bits of the main memory address, a range or a task into thedata register 82. Under firmware control, the information in the addressshift register 70 is clocked through the AMUX 72 and the OR logic unit83 to the A1 input of the arithmetic unit 85. Further, in response to afirmware command on line 106, the arithmetic control unit 91 issues amode to the arithmetic unit 85 to select the A1 input. The A1 input tothe arithmetic unit thereupon is supplied to the input of the scratchpadaddress counter 79, and loaded into the address counter under a firmwarecommand supplied to control line 114.

Two bits of the address shift register output on data cable 73 aresupplied to the A1 input of index register 74 to indicate the diskdevice from which information is to be read. Under firmware control byway of control line 74a, the two identification bits are loaded into theindex register. The output of the index register is supplied to theselector 115 as is the two high-order bits of the address counter 79.

The firmware further initializes the address counter 79 by issuing anup/down signal on control line 79a, and a clock signal on control line79b. The counter is commanded to count up or down at the rate indicatedby the firmware generated clock signal. In response to the inputs fromthe index register and the address counter, the selector 115 addressesthe scratchpad memory unit 81. The data resident in the data register 82thus is transferred under firmware control to the scratchpad memoryaddress indicated by selector 115 by way of a data path through the AMUX72, the OR logic unit 83 and data cable 117. The configuration words Aand B, a main memory address, a range, and a task thereby are loadedinto scratchpad memory.

Upon completing the memory store operation, the firmware accesses thefunction code in the address shift register 70 to determine whether atask is indicated. More particularly, the firmware supplies a hex code 07 by way of cable 86 to the A1 input of BMUX 84. The BMUX is selected tothe A1 input via a firmware control signal on control line 84a. The hexcode thereupon is routed through the arithmetic unit 85 and stored inaccumulator 75. Thereafter, the output of address counter 79 ischannelled through the AMUX 72 and the OR logic unit 83 to the A1 inputof arithmetic unit 85. Under firmware control, the arithmetic unitcompares the code in the accumulator 75 with the output of the addresscounter 79. If a match occurs, a task is indicated and the test logicunit 102 issues a signal to the firmware by way of control line 126 toinitiate the execution of a next sequence of microinstructions. Inaddition, the bus logic unit 128 in response to firmware control signalson line 130 sets the addressed disk device channel busy. Thereafter, anyfurther information which is sent by way of megabus 13 to address thedevices for which the present task is assigned shall be acknowledgedwith a NAK status signal.

Upon detecting the presence of a task, the firmware accesses the taskstored in the scratchpad memory 81 and transfers that informationthrough the AMUX 72 and OR logic unit 83 to the arithmetic unit 85.Under firmware control, the arithmetic unit 85 and the test logic unit102 tests the task information to determine the command to be executed.For example, the task may indicate that a disk seek, a recalibrate, aread or a write operation is required. The results of these tests aresupplied by the test logic unit 102 to firmware by way of control cable126.

In a write operation wherein data is to be read from main memory unit 12and written on a disk device, the adapter logic unit 29 under firmwarecontrol issues a strobe to the device adapter 14 to load an internaldata counter with a count of four. Further, the adapter logic unit 29 iscommanded to issue a sequence of four strobes to load configurationwords A and B into a data buffer of the device 14. More particularly,the information is routed under firmware control from the scratchpadmemory 81 through the BMUX 84 and the arithmetic unit 85 to data cables92 and 94 leading to the device adapter 14.

Before the logic unit 29 issues a BEGIN EXECUTION command to the deviceadapter 14, the megabus 13 must be set up for the transfer of data. Thefirmware supplies two dummy bytes of offset range to the BMUX 84 by wayof cable 86, and controls the transfer of the bytes through thearithmetic unit 85 and along data control 96 to the bus address register136. The loading of the address register 136 is accomplished underfirmware control on line 136a. The firmware then accesses the rangeinformation stored in the scratchpad memory unit 81, and transfer thatinformation through the BMUX 84 and the arithmetic unit 85 to data cable96 leading to the bus address register 136. As the range data is loadedinto register 136, the offset range data is transferred to control unit77. The two bytes of range data thereafter are transferred from the busaddress register 136 into the control unit 77 under firmware control,and three bytes of address information in scratchpad memory are storedinto the bus address register 136. The MPDC thereby is prepared forreceiving data from main memory for writing on the indicated diskdevice.

To initiate a data transfer, the firmware accesses the scratchpad memory81 to transfer the MPDC channel number previously supplied by the CPU11, and transfer the channel number through the BMUX and arithmetic unit85 for storage in the bus data register 100. At this time, the mainmemory address from which data is to be initially read resides in thebus address register 136, and the MPDC channel destination numberresides in bus data register 100.

The firmware also supplies bus logic commands to the BMUX 84 by way ofcable 86, and stores those commands in the accumulator 75. From theaccumulator, the commands are supplied by way of data cable 103 to thebus logic unit 128. These commands in logical sequence instruct the buslogic unit 128 to issue a response-required request to main memory toacknowledge that data is to be supplied to the MPDC, to issue a mainmemory channel number identifying the main memory unit as the systemunit addressed, and to issue an indication as to whether the MPDC is ina byte or a word mode.

In normal operation, a read or a write command is always preceded by aseek command wherein the firmware commands the adapter device 14 toposition the read-write heads of the disk device. In addition, thedevice adapter is instructed to select the proper head from which theinformation is to be read or written. The device adapter 14 thencompares the configuration words A and B with data read from the surfaceof the disk. If a match is detected which indicates that a designatedrecord is in position, the device adapter 14 issues a write command tothe disk device and begins to write a header gap on the record. Duringthis period, the device adapter 14 also issues an interrupt by way ofcontrol line 110 to the hardware control unit 108. In response thereto,the control unit issues a signal to the A1 input of test logic unit 102to notify firmware by way of control cable 126 that control should beturned over to the before-described system hardware. Firmware thereuponissues an enable hardware command to control line 109, and furtherissues commands by way of control line 134 to the data control unit 113to control the operation of FIFO unit 131 in requesting data frommemory. The FIFO unit 131 operates to anticipate the availability ofspace in the data FIFO unit 118 for the receipt of data word from mainmemory. More particularly, each time the bus logic unit 128 requests adata word from main memory, a dummy byte is loaded into the FIFO unit131. The bus logic unit 128 thereafter requests a second word of dataonly if the dummy byte has dropped from the input register of the FIFOunit 131 into the FIFO stack. Main memory thereupon issues data words byway of megabus 13 to the data register 82.

When the bus logic unit 128 has requested a data word from main memoryand accepted the word, the logic unit issues a signal to the A2 input ofdata control unit 113. In response thereto, the control unit issues acommand on control line 135 to the data FIFO unit 118 to store data fromthe data register 82. The above-described operation is repeated untilthe data FIFO unit 118 is filled with 32 bytes of data.

When the data FIFOs are filled, unit 118 issues a signal by way ofcontrol lines 118a to the hardware control unit 108. Control unit 108thereupon issues a strobe by way of control line 111 to the adapterlogic unit 29. Logic unit 29 in turn issues a strobe to the deviceadapter 14 to indicate that a data byte may be transferred from the dataFIFOs to the device adapter 14. The same strobe is applied by way ofcontrol lines 29a and 118b to the TOP (transfer out parallel) terminalof data FIFO unit 118. The D1 and D2 outputs of the FIFO unit thereuponare transferred through the OR Logic 83 and through the arithmetic unit85 to the device adapter 14 by way of data cables 92 and 94.

The logic unit 29 strobe also is applied by way of control line 29a tothe data control unit 113. The reception of two of such strobesindicates that a two-byte data word has been transferred from the dataFIFO unit 118 to device adapter 14. The data control unit 113 thereuponissues a control signal to the A2 input of FIFO unit 131 to drop a dummybyte out of the output register of the FIFO stack. The input register ofthe FIFO unit thereby is emptied, and issues a signal to the bus logicunit 128 to initiate a request for an additional data word from mainmemory. The above-described process continues until the device adapterunit 14 indicates that a record has been written.

It is to be understood that the device adaptor 14 controls the writeoperation of the disk device. As the data is being written on the disk,the device adapter signals the test logic unit 102 by way of controlline 125 to cease supplying data until the internal buffers of thedevice adapter have been emptied. During this period, the test logicunit 102 notifies the firmware control system that control may betransferred from the hardware to the firmware. When the device adapter14 is ready to receive additional data, the logic state of control line125 is changed. The test logic unit 102 thereupon notifies the firmwareto return control to the hardware to resume the data transfer. Thisprocess continues until a data transfer is completed as indicated by arange count of zero.

Each time the bus logic unit 128 requests an additional data word, thedata control unit 113 under system hardware control decrements the rangecounters of control unit 77 by one. Further, after a data requestincluding a main memory address has been issued to the megabus 13 andaccepted by the main memory unit 12, the control unit 77 increments thebus address register 136 by two and decrements the range counters byone. When the range count has been exhausted, the range control unit 77issues an end-of-range (EOR) signal by way of control lines 77a and 102bto the device adapter 14 and the test logic unit 102, respectively.

It is to be noted that the control cable 125 includes two interruptlines. A first interrupt line is a firmware request line to indicatethat control should be returned to firmware while the device adapter 14is between records. The second interrupt line is used to notify firmwarethat non-data service requests may be serviced. Such action normallyindicates that there is some type of error in the device adapter 14.

If the EOR signal is issued during a record or at the end of a record onthe disk device, the firmware will terminate the write order. If the EORsignal is received by the device adapter 14 before an end of recordoccurs, the device adapter fills the remaining portion of the recordwith dummy bytes. If an EOR signal does not occur, however, and there isno device adapter error indicated on interrupt cable 127, then thefirmware will update the configuration words A and B in device adapter14 to point to a next logical sector of the disk device.

FIG. 6

FIG. 6 illustrates in functional block diagram form a firmware controlsystem for controlling the operation of the system illustrated in FIGS.4 and 5.

The 12-bit output of a 16-bit return register 200 is connected to the A1input input of a selector 201. The 12-bit output of the selector 201 inturn is applied to the input of a 16-bit microprogram address counter202, and the 12-bit output of the address counter is connected to theinput of a 4.0K by 16-bit Read Only Store (ROS) 203 having themicroinstructions of a microprogram stored therein. The 16-bit D1 outputof the ROS is connected to the input of a 16-bit microprograminstruction register 204, and the D2 output of the ROS is applied to theA3 input of the selector 201.

The microprogram instruction register 204 further receives a controlsignal from the test logic unit 102 of FIG. 4 by way of a control line126 to reset or clear the register. The 16-bit output of themicroprogram instruction register 204 is applied to the input of adecoder 205, to the A1 input of return register unit 200, and to the A1input of a firmware distributor 206. A one-bit output of the register204 is applied to the LD input of return register 200.

The D1 output of decoder 205 is applied to the A2 input of the selector201, and the D2 output of the decoder is applied to the A2 input ofreturn register unit 200. Further, the D3 output of decoder 205 isapplied to the A2 input of distributor 206. The D1 output of thedistributor is applied to control line 130 leading to the bus logic unit128, and the D2 output is applied to control line 134 leading to thedata control unit 113. The D3 output of distributor 208 is applied tocontrol line 127 connected to the A2 input of adapter logic unit 29, andthe D4 output is applied to control line 106 leading to the arithmeticcontrol unit 91. The D5 output is supplied to control line 109 connectedto the A1 input of hardware control unit 108, and the D6 output isconnected to line 137 leading to the A3 input of control unit 77. The D7output is connected to control cable 86, and the D8 output is applied tocontrol line 114 carrying load commands to the counter 79. The D9 outputis applied to control line 116, and the D10 output is applied to controlline 124. The D11 output is applied to control line 70b, the D12 outputto control line 72a and the D13 output to control line 84a. The D14output is applied to line 75a, the D15 output to line 74a and the D16output to line 79a. The D17 output is applied to line 79b and the D18output to line 136a. The D19 output of distributor 206 is applied to theLD input of counter 202, the clock input of which is supplied by thesystem hardware by way of control line 207. Control line 207 further isconnected to the LD input of register 204.

The 16-bit firmware commands stored in ROS 203 are divided into fourfields: the OPCODE, the AMUX 72 select, the BMUX 84 selected and themixcellaneous fields. The firmware commands further are segmented intoseven categories each representative of bit configurations forperforming a designated operation. The seven basic categories offirmware commands are: miscellaneous commands, bus logic commands, ALUcommands, constant value data commands, memory commands, test commands,and branch commands. Each of the firmware categories is identified by aparticular OPCODE which is a binary decode of bits 0, 1 and 2 of ROS203.

In operation, the microprogram address counter 202 is loaded fromselector 201 under firmware control, and thereafter clocked by hardwaresystem control signals on line 207. The address counter addresses theROS 203, which in response thereto supplies microinstructions to theinstruction register 204. The register 204 loads the microinstructionsunder hardware control, and applies the microinstruction bitconfiguration to decoder 205, distributor 206 and return register 200.

The order in which the microinstruction sequences stored in ROS 203 areexecuted may be controlled in any of several ways. The test logic unit102 may issue a reset signal causing a no-op instruction to occur in theinstruction register 204. The instruction register thereupon skips thecurrent instruction in the register, and proceeds to the next occurringinstruction. In the alternative, the address counter 202 may be loadedwith a microinstruction address formed from Read Only Store 203 andregister 200. The firmware control system of FIG. 6 thus offerssignificant versatility in the execution of microprograms.

As each microinstruction addressed in ROS 203 is loaded into register204, the instruction bit configuration and a binary code from decoder205 identifying the instruction category are applied to distributor 206.In response thereto, the distributor applies firmware control signals tothe system of FIGS. 4 and 5 as before described.

A copy of the microprogram stored in the ROS 203 is reproduced in itsentirety, and attached hereto as Appendix A.

The operation of decoder 205 and firmware distributor 206 may better beunderstood by reference to Tables A-K. The OPCODES are defined in TableA, which provides a pointer to one of Tables B-K. For example, theOPCODE 0 0 0 refers to the miscellaneous commands of Table B. The OPCODEof 0 1 0 refers to Table C, the OPCODE 0 1 1 to Table D, the OPCODE 1 00 to Table E, and the OPCODE 1 0 1 to Table F. Further, the OPCODE 1 1 0refers to Table G and the OPCODE 1 1 1 to Table I.

                  Table A                                                         ______________________________________                                        Opcode Instructions                                                           MICROINSTRUCTIONS                                                             ______________________________________                                        0 0 0            MISCELLANEOUS                                                0 0 1            RFU                                                          0 1 0            BUS LOGIC                                                    0 1 1            ALU                                                          1 0 0            CONSTANTS                                                    1 0 1            MEMORY                                                       1 1 0            TEST                                                         1 1 1            BRANCH                                                       ______________________________________                                    

                                      Table B                                     __________________________________________________________________________    Miscellaneous Commands                                                         OPERATION          BINARY VALUE  MNEMONIC                                                                              HEX CODE                            __________________________________________________________________________    NO OPERATION        0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0                                                             NOP     0 0 0 0                             CLEAR COMMAND       0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0                                                             CLR     1 0 0 0                             SET ERROR FLOPS     0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0                                                             SEF     0 8 0 0                             ENABLE HARDWARE DATA PATH                                                                         0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0                                                             EHP     0 6 0 0                             DISABLE HARDWARE DATA PATH                                                                        0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0                                                             DHP     0 2 0 0                             RESET DIAGNOSTIC MODE                                                                             0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0                                                             RSD     0 0 8 0                             SET DIAGNOSTIC MODE 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0                                                             STD     0 1 8 0                             HALT                0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0                                                             HLT     0 0 4 0                             RFU                 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0                                                             --      0 0 2 0                             CLEAR FLOPS AND REGISTERS                                                                         0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0                                                             CRF     0 0 1 0                             RESET DEVICE ADAPTER                                                                              0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0                                                             RDA     0 0 0 8                             SET QLT (BLT DONE)  0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0                                                             QLT     0 0 0 4                             SET BUS ACK         0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0                                                             SBA     0 0 0 2                             RFU                 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1                                                             --      0 0 0 1                             ENABLE READ PATH    0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0                                                             ERP     0 6 0 0                             ENABLE WRITE PATH   0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 1                                                             EWP     0 6 0 1                             __________________________________________________________________________

                                      Table C                                     __________________________________________________________________________    Bus Logic Commands                                                             OPERATION       BINARY VALUE    MNEMONIC                                                                              HEX CODE                             __________________________________________________________________________    INCREMENT ADDRESS CNTR.                                                                        0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0                                                               IAC     4 1 0 0                              RESET STATUS     0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0                                                               RST     4 0 8 0                              DECREMENT RANGE CNTR.                                                                          0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0                                                               DRC     4 0 4 0                              CYCLE            0 1 0 A.sub.1 A.sub.2 A.sub.3 0 0 0 0 1 0 0 0 0                                               CYCub.0                                      SET CHANNEL READY                                                                              0 1 0 0 0 0 0 0 0 0 0 1 1 0 0 0                                                               SCR     4 0 1 8                              RESET CHANNEL READY                                                                            0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0                                                               RCR     4 0 1 0                              SET REGISTER BUSY                                                                              0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0                                                               SRB     4 0 0 4                              RESET REGISTER BUSY                                                                            0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0                                                               RPB     4 0 0 2                              RESET INTERRUPT LATCH                                                                          0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1                                                               RIL     4 0 0 1                              CLEAR BUS        0 1 0 0 0 0 0 0 1 0 0 0 0 1 1 0                                                               CLB     4 0 8 6                              __________________________________________________________________________     A.sub.0 A.sub.1 A.sub.2 A.sub.3 = SELECT AOP MUX INPUT.                  

                                      Table D                                     __________________________________________________________________________    ALU Commands                                                                   OPERATION    BINARY VALUE         MNEMONIC                                                                              HEX CODE                           __________________________________________________________________________    AOP NEGATION  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 0 0 0 1                   A.sub.0              ANT     N/A                                BOP NEGATION  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 1 0 1 1                   A.sub.0              BNT     N/A                                ZERO ALU      0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 0 1 1 1                   A.sub.0              ZER     N/A                                AOP TRANSFER  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 1 1 1 1                   A.sub.0              XFA     N/A                                BOP TRANSFER  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 0 1 0 1                   A.sub.0              XFB     N/A                                NOR A TO B    0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1  C S 0 0 0 1                    1 A.sub.0            NOR     N/A                                NAND A TO B   0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 1 0 0 1                   A.sub.0              NND     N/A                                XOR A TO B    0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 1 1 0 1                   A.sub.0              XOR     N/A                                XNOR A TO B   0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 0 0 1 1                   A.sub.0              XNR     N/A                                AND A TO B    0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 0 1 1 1                   A.sub.0              AND     N/A                                OR A TO B     0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 1 1 0 1                   A.sub.0              ORR     N/A                                AOP PLUS ONE  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 0 0 0 0                   A.sub.0              INC     N/A                                AOP MINUS ONE 0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 1 1 1 0                   A.sub.0              DEC     N/A                                SUBTRACT B FROM A                                                                           0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 0 1 1 0 0                   A.sub.0              SUB     N/A                                ADD A to B    0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C S 1 0 0 1 0                   A.sub.0              ADD     N/A                                LEFT SHIFT AOP                                                                              0 1 1 A.sub.1 A.sub.2 A.sub.2 B.sub.0 B.sub.1 C S 1 1 0 0 0                   A.sub.0              LSH     N/A                                CARRY OUT IN  0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 1 S X X X X X                   A.sub.0              COTI    N/A                                STORE RESULT IN AOP                                                                         0 1 1 A.sub.1 A.sub.2 A.sub.3 B.sub.0 B.sub.1 C 1 X X X X X                   A.sub. 0             SRIA    N/A                                __________________________________________________________________________     A.sub.0 A.sub.1 A.sub.2 A.sub.3 = AOP REG. SELECT                             B.sub.0 B.sub.1 = BOP REG. SELECT                                             C = DETERMINE CARRY IN                                                        S = DETERMINE A OR B RESULT STORAGE                                      

                                      Table E                                     __________________________________________________________________________    Constant Commands                                                              OPERATION        BINARY VALUE       MNEMONIC                                                                              HEX CODE                         __________________________________________________________________________    LOAD CONSTANT TO AOP                                                                            1 0 0 A.sub.1 A.sub.2 A.sub.3 C C C C C 0 C 0 C                                                  LCN     N/A                              AOP ANDED WITH CONSTANT                                                                         1 0 0 A.sub.1 A.sub.2 A.sub.3 C C C C C 0 C 1 C                                                  ACN     N/A                              AOP ORED WITH CONSTANT                                                                          1 0 0 A.sub.1 A.sub.2 A.sub.3 C C C C C 1 C 0 C                                                  OCN     N/A                              __________________________________________________________________________     A.sub.1 A.sub.2 A.sub.3 = AOP REG. SELECT                                     C = VALUE OF CONSTANT                                                    

                                      Table F                                     __________________________________________________________________________    Memory Commands                                                                OPERATION        BINARY VALUE      MNEMONIC                                                                              HEX Code                          __________________________________________________________________________    MEMORY WRITE      1 0 1 A.sub.1 A.sub.2 A.sub.3 1 0 0 0 0 0 0 0 0                               A.sub.0           MWT     N/A                               INCREMENT SP ADDRESS                                                                            1 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0                                                                 IMA     A100                              DECREMENT SP ADDRESS                                                                            1 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0                                                                 DMA     A008                              MEMORY WRITE & INC                                                                              1 0 1 A.sub.1 A.sub.2 A.sub.3 1 1 0 0 0 0 0 0 0                                                 WIAub.2 N/A                               MEMORY WRITE & DEC                                                                              1 0 1 A.sub.1 A.sub.2 A.sub.3 1 0 0 0 0 0 1 0 0                                                 WDAub.0 N/A                               SET SP TEST MODE  1 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0                                                                 SPT     A080                              RFU               1 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0                                                                 --      A040                              LOAD REQUESTING CHANNEL                                                                         1 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0                                                                 LRC     A020                              LOAD INDEX REG. WITH AOP                                                                        1 0 1 A.sub.1 A.sub.2 A.sub.3 0 0 0 0 1 1 0 0 0                                                 LIRub.0 N/A                               SET MODULE BAD PARITY                                                                           1 0 1 0 0 0 0 0 0 0 1 0 0 1 0 0 MBP                                                             A004                                      RFU               1 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0                                                                 --      A002                              __________________________________________________________________________     A.sub.0 A.sub.1 A.sub.2 A.sub.3 = AOP REG. SELECT.                       

                                      Table G                                     __________________________________________________________________________    Test Commands                                                                  OPERATION                                                                              BINARY VALUE         MNEMONIC                                                                              HEX CODE                               __________________________________________________________________________    TEST FOR ZERO                                                                           1 1 0 A.sub.1                                                                      A.sub.2 A.sub.3 0 0                                                                 0 1 T T                                                                            T T T A.sub.0                                                                      TFZ     N/A                                    TEST FOR ONE                                                                            1 1 0 A.sub.1                                                                      A.sub.2 A.sub.3 0 0                                                                 1 0 T T                                                                            T T T A.sub.0                                                                      TFO     N/A                                    RETURN    1 1 0 0                                                                            0 0 1 0                                                                             0 0 0 0                                                                            0 0 0 0                                                                            RTN     C200                                   __________________________________________________________________________     A.sub.0 A.sub.1 A.sub.2 A.sub.3 = AOP REG. SELECT                             TTTTT = TEST MUX INPUT.                                                  

                                      Table H                                     __________________________________________________________________________    Test Parameters                                                               MNEMONIC                                                                              FUNCTION  HEX CODE                                                                             DESCRIPTION                                          __________________________________________________________________________    TAHR    HDTSRO+00 00     ADAPTER HARDWARE REQUEST                             TBCA    SHRCOM+00 01     BUS CYCLE ACTIVE                                     TRSP    BSRSVP+30 02     BUS RESPONSE REQUIRED                                TEQZ    ALUEQF+00 03     ALU OUTPUT EQUALS 00                                 TEQF    ALUEQF+00 04     ALU OUTPUT EQUALS FF                                 TCOT    ALUCOT+00 05     ALU CARRY OUT                                        TREQ    CREREQ+00 06     CHANNEL REQUEST                                      TACK    ACKRSF+00 07     BUS ACK RESPONSE                                     TAX0    ALUAXO-00 08     AOP MULTIPLEXER, BIT O                               TAX1      ↓  1                                                                           09       ↓  BIT 1                                    TAX2      ↓  2                                                                           0A       ↓  BIT 2                                    TAX3      ↓  3                                                                           0B       ↓  BIT 3                                    TAX4      ↓  4                                                                           0C       ↓  BIT 4                                    TAX5      ↓  5                                                                           0D       ↓  BIT 5                                    TAX6      ↓  6                                                                           0E       ↓  BIT 6                                    TAX7    ALUAX7-00 0F     AOP MULTIPLEXER, BIT 7 -TORZ DRCAR3-00 10 OFFSET                              RANGE ZERO                                           TRGZ    EOR(xxx)+00                                                                             11     RANGE ZERO                                           TSBS    SBSOBS+00 12     SINGLE BYTE STORED                                   TSAW    SPAWRP+00 13     SP ADDRESS WRAPAROUND                                TADB    BUSY(xx)+ 00                                                                            14     ADAPTER BUSY                                         TNDR    NDTSRQ+00 15     NON-DATA SERVICE REQUEST                             TORH    OFRNGZ=00 16     OFFSET RANGE HISTORY                                 TDCN    MYDCNN-00 17     MY DATA CYCLE NOW                                    TBSY    BDRBSY+00 18     BUS DATA REGISTER BUSY                               TUBR    UBRO(xx)+00                                                                             19     UNSOLICITED BUS REQUEST                              TINT    RESINT+00 1A     RESUME INTERRUPT                                     TNAK    NAKRSP+00 1B     NAK RESPONSE                                         TBYT    BSAD23+00 1C     BYTE MODE                                            TATY    BSPYCK+00 1D     BUS PARITY CHECK                                     TNBR    NOHTRQ+00 1E     NO BUFFER REQUEST                                    TFDR    FDTSRQ+00 1F     FIRMWARE DATA SERVICE REQUEST                        __________________________________________________________________________

                                      Table I                                     __________________________________________________________________________    Branch Commands                                                                OPERATION                                                                             BINARY VALUE      MNEMONIC                                                                              HEX CODE                                   __________________________________________________________________________    GO TO    1 1 1 1 A A A A A A A A A A A A                                                                  GTO    FXXX                                       LOAD RETURN                                                                            1 1 1 0 A A A A A A A A A A A A                                                                  LRA    EXXA                                       __________________________________________________________________________     A = BRANCH ADDRESS.                                                      

                                      Table J                                     __________________________________________________________________________    AOP Multiplexer Input Selection                                                       SELECTED REGISTER       SELECTED REGISTER                              A.sub.0                                                                         A.sub.1                                                                         A.sub.2                                                                         3                                                                               ##STR1##        MNEMONIC                                                                              (SRIA)*                MNEMONIC              __________________________________________________________________________    0 0 0 0 ACCUMULATOR     AACU    ACCUMULATOR            AACU                   0 0 0 1 SCRATCH PAD MEMORY                                                                            ASPM    SCRATCH PAD MEMORY     ASPM                   0 0 1 0 SCRATCH PAD ADDRESS                                                                           ASPA                                                                                   ##STR2##              ASPA                   0 0 1 1 INDEX REGISTER  AIDX    SCRATCH PAD ADDRESS (INDEXED)                                                                        ASPA1                  0 1 0 0 ADAPTER DATA REGISTER                                                                         AAD0    ADAPTER DATA REGISTER  AAD0                   0 1 0 1 ADAPTER DEVICE ID                                                                             AAD1    ADAPTER DATA COUNTER   AAD1                   0 1 1 0 ADAPTER STATUS 1                                                                              AAD2    ADAPTER COMMAND REGISTER                                                                             AAD2                   0 1 1 1 ADAPTER STATUS 2                                                                              AAD3    ADAPTER UNIT SELECT    AAD3                   1 0 0 0 BUS ADDRESS OUT ABUS1   BUS REGISTER IN        ABUS1                  1 0 0 1 BUS DATA OUT 1  ABUS2   BUS DATA IN 1          ABUS2                  1 0 1 0 BUS DATA OUT 2  ABUS3   BUS DATA IN 2          ABUS3                  1 0 1 1 BUS RANGE OUT   ABUS4   BUS ADDRESS IN         ABUS4                  1 1 0 0 ADAPTER RFU     AAD4    RESET ADAPTER INDEX COUNT                                                                            AAD4                   1 1 0 1 ADAPTER RFU     AADS    ADAPTER STATUS & FIFO CLEAR                                                                          AAD5                   1 1 1 0 ADAPTER RFU     AAD6    ADAPTER SEEK PULSE     AAD6                   1 1 1 1 ADAPTER RFU     AAD7    ADAPTER DATA BYTE TAKEN                                                                              AAD7                   __________________________________________________________________________     ##STR3##                                                                 

                  Table K                                                         ______________________________________                                        BOP MUX Input                                                                 B.sub.0                                                                            B.sub.1                                                                              SELECTED DATA INPUT MNEMONIC                                      ______________________________________                                        0    0      ACCUMULATOR         BACU                                          0    1      SCRATCH PAD MEMORY  BSPM                                          1    0      BUS STATUS          BBST                                                       0-3 (ZEROS)                                                                   4 BUS YELLOW IND.                                                             5 BUS NAK                                                                     6 BUS PARITY ERROR                                                            7 BUS RED IND.                                                   1    1      BOP CONSTANT                                                      ______________________________________                                    

The instructions of Tables C-G and I include A-fields comprised of bitsA₀ -A₃. Each of the A-fields refer to registers providing data to theAMUX 72 of FIG. 4. Table D further includes instructions having aB-field comprised of bits B₀ and B₁. The B-field is defined by Table K,wherein it is indicated that the BMUX may be selected to the accumulator75, the scratchpad memory unit 81, to the bus logic unit 128 by way ofcable 88 for bus status inputs, and to the firmware control system byway of cable 86 for a constant value input. Where two-byte arithmetic isbeing performed by the arithmetic unit 85, the C-field of Table D isused to provide a carry-in feature wherein the result of a previous AU85 operation may be used in a subsequent operation. The F-field of theinstructions of Table D provides a command to store the result of the AU85 operation into a register designated by the A-field. The remaininglow-order bits of Table D refer to the mode select bits for commandingthe AU 85 to perform the indicated operation.

The instruction set of Table E includes a C-field for constant values,and the low-order bits of the instructions of Table F provide for thegeneration of strobes for loading the registers indicated by the A-fieldthereof. The instruction set of Table G includes test or T-fields whichare defined by the entries of Table H. The A-field of Table I refers tothe address of the microprogram to which a transfer is to be made.

Table L provides a cross-reference between the mnemonics used in theTables A-K and the component parts of the system as described in FIGS.4-8.

                  TABLE L                                                         ______________________________________                                        Microinstruction Mnemonic                                                                      Hardware Device                                              ______________________________________                                        RFU              Reserved For User                                            Bus Logic        Bus logic unit 128                                           ALU              Arithmetic Unit 85,                                                           Arithmetic Control Unit 91,                                                   Accumulator 75                                               Accumulator      Accumulator 75                                               Scratchpad Memory                                                                              Scratchpad Memory Unit 81                                    Scratchpad Address                                                                             Scratchpad Address Counter 79                                BLT              Bus Logic Tests                                              Address Counter  Bus Address Counters 300,                                                     302 and 303                                                  Range Counter    Range Counters 306-309                                       AOP              AMUX 72                                                      BOP              BMUX 84                                                      SP Address       Scratchpad Address Counter                                   Memory           Scratchpad Memory unit 81                                    ______________________________________                                    

FIG. 7

FIG. 7 illustrates in a more detailed functional block diagram form therange and offset range control unit 77, the address multiplexer 133 andthe bus address register 136.

A bus address counter 300 receives data from AU 85 on an 8-bit datacable 96, and load commands from firmware on control line 136a. Theclock input to counter 300 is connected to the clock input of a busaddress counter 302, to the clock input of a bus address counter 303,and to the output of an address clock logic unit 304. The 8-bit outputof the counter 300 is applied to the megabus 13 by way of a data cable305, and to the data input of counter 302.

In the preferred embodiment described herein, address counters 300, 302and 303 form a 24-bit memory address up counter.

The load input of counter 302 is connected to control line 136a and tothe load inputs of counter 303, a range counter 306, a range counter307, an offset range counter 308, and an offset range counter 309. Thecounters 306 and 307 form a 16-bit range down counter, and the counters308 and 309 form a 16-bit offset range down counter. The 8-bit output ofcounter 302 is applied to the A1 input of an address multiplexer 310,and to the data input of counter 303. The 8-bit output of counter 303 isapplied to the A1 input of an address multiplexer 311, and to the datainput of range counter 306.

Address multiplexer 310 also receives at its A2 input data from dataregister 82 of FIG. 4 by way of cable 139. The 8-bit output of themultiplexer is applied to a data cable 312 leading to megabus 13. Theselect (SEL) input to multiplexer 310 is supplied by the bus logic unit128 on a control line 313.

The address multiplexer 311 also receives data from the data register 82by way of data cable 140, and supplies 8 bits of data to a data cable314 leading to megabus 13. The SEL input to multiplexer 311 is connectedto the SEL input of multiplexer 310.

The 8-bit output of range counter 306 is connected to the input of rangecounter 307. The output of counter 307 in turn is applied to the inputof counter 308, and the 8-bit output of counter 308 is applied to theinput of counter 309. The 8-bit output of counter 309 in turn is appliedto control line 76 leading to the A3 input of AMUX 72.

The clock source for the system of FIG. 7 is a 4.0 MHz oscillator 315,which supplies clock signals to address clock logic unit 304 and a rangeclock logic unit 316. The logic unit 304 receives enable signals frombus logic unit 128 and from firmware on control lines 317 and 318,respectively. In response thereto, the logic unit 304 issues incrementcommands to counters 300, 302 and 303.

The range clock logic unit 316 receives enable signals from bus logicunit 128, the firmware and the data control unit 113 by way of controllines 319-321, respectively. Further, the control unit 113 supplies anoffset range enable signal to the EN4 input of logic unit 316. Whenenabled, the logic unit 316 supplies decrement commands to counters306-307 or counters 308-309.

If data is to be read from or written onto a disk device controlled bythe device adapter 14, the CPU 11 of FIG. 1 supplies a channeldestination number and a function code to the address shift register 70of FIG. 4 as before described. In addition, the CPU suppliesconfiguration words A and B, a main memory address, a range count, anoffset range count, a task and a status request to the data register 82.The firmware accesses the function code in register 70 to detect theaddress in scratchpad memory unit 81 in which the data of register 82 isto be stored.

The firmware then serially shifts seven bytes of data a byte at a timefrom scratchpad memory unit 81 into address counters 300, 302 and 303,range counters 306 and 307, and offset range counters 308 and 309. Uponcompletion of the load operation, a main memory address resides inaddress counters 300, 302 and 303, a range count in counters 306-307,and an offset range count in counters 308-309.

In a read operation wherein data is to be read from the disk device andwritten into main memory unit 12, the megabus 13 is supplied both dataand a 24-bit address in main memory in which the data is to be written.More particularly, the data resides in the bus data register 100. When adata word comprising two data bytes is to be transferred from the MPDC10 to the megabus 13, the bus logic unit 128 selects the multiplexers310 and 311 to the A1 inputs. The main memory module to which the datais to be transferred thereby is made available to the megabus 13. Themain memory address in which the transferred data is to be writtenthereupon is supplied from address counters 300, 302 and 303 to cables305, 312 and 314 respectively. Each time the main memory unit issues anacknowledgement signal and accepts data into the indicated address, themain memory address in counters 300, 302 and 303 is incremented by two.

During a data transfer from device adapter 14 to MPDC 10, the datacontrol unit 113 of FIG. 5 issues a logic one signal to control line 322each time a data byte is transferred. The range clock logic unit 316 isenabled thereby to decrement the offset range counters 308 and 309. Theoutput of counter 309 is applied by way of cable 76 to the AMUX 72 andthe AU 85 of FIG. 4. As long as the offset range count is greater thanzero, the data bytes are ignored and are not transferred to megabus 13.When the offset range count is exhausted, however, data transfer controlswitches from the offset range counters to the range counters 306 and307. More particularly, the data control unit 113 disables the EN4 inputto logic unit 316, and thereafter issues enable signals to the EN3 inputof the logic unit by way of control line 321. The logic unit 316 inresponse thereto decrements the range counters each time a data byte istransferred from the device adapter 14 to the MPDC 10. Each of the databytes transferred after control switches to the range counters aretransferred to megabus 13.

When the range count in counters 306 and 307 is exhausted, counter 307issues an end-of-range (EOR) signal on lines 77a and 102b as beforedescribed.

A write operation wherein data is read from main memory and written ontoa disk device is accomplished in a manner similar to that of the readoperation. A channel destination number and a function code are loadedinto the address shift register 70, and data including configurationwords A and B, a main memory address, a range count, a task and a statusrequest are loaded from data register 82 into scatchpad memory unit 81.An offset range count is not used in writing data onto a disk device.

After the device adapter 14 has positioned the write heads of the diskdevice, and issued a hardware service request signal on line 110 of FIG.4, firmware loads two dummy bytes into the offset range counters 308 and309, a range count into counters 306 and 307, and a main memory addressinto counters 300, 302 and 303. The firmware further transfers an MPDCchannel number from scratchpad memory unit 81 to the bus data register100, and thence through data multiplexer 122 to megabus 13. Underfirmware control, the bus logic unit 128 issues a response-required datarequest to main memory, and selects the multiplexers 310 and 311 totheir A2 inputs to supply the main memory channel number in addressshift register 70 to megabus 13. The bus logic unit thereafter selectsthe multiplexers 310 and 311 to their A1 inputs to supply the mainmemory address to megabus 13.

Each time the bus logic unit 128 requests an additional data byte frommain memory, the logic unit also issues a logic one signal to controlline 319 to enable the range clock logic unit. The range counters 306and 307 thereupon are decremented by one. Further, after a data requestand a main memory address have been issued to megabus 13 and accepted bythe main memory unit 12, the bus logic unit 128 enables the EN1 input ofthe address clock logic unit 304. In response thereto, the addresscounters 300, 302 and 303 are incremented by two.

When the range count has been exhausted, counter 307 issues an EORsignal to lines 77a and 102b as before described. The data transfer frommain memory unit 12 to disk device 14 thereby is designated complete.

The system of FIG. 7 represents a significant improvement over priorfirmware data transfer controls, which required too much time forbookkeeping. Previously, bookkeeping parameters were stored in memory,and had to be retrieved and restored when a parameter was updated. Inthe instant hardware/firmware invention, the bus address counters 300,302 and 303, the range counters 306-307, and the offset range counters308-309 may be loaded serially to substantially decrease the number ofmicroinstructions required in a load operation. Further, during a datatransfer, the counters may be incremented or decremented under hardwarecontrol to accommodate an increased data flow rate.

FIG. 8

FIG. 8 illustrates in detailed logic diagram form the FIFO unit 131 ofFIG. 5.

In referring to the electrical schematics illustrated in the Figures, itis to be understood that the occurrence of a small circle at the inputof a logic device indicates that the input is enabled by a logic zero.Further, a circle appearing at an output of a logic device indicatesthat when the logic conditions for that particular device are satisfied,the output will be a logic zero.

An AND gate 400 has one input connected to a control line 401, and asecond input connected to both a control line 402 and one input of anAND gate 403. A second input to gate 403 is connected to a control line404 leading to line 110 of FIG. 4, and a third input is connected to acontrol line 405.

The output of gate 400 is connected to the D input of a flip-flop 405,and to the D input of a flip-flop 406. The output of gate 403 is appliedto the trigger (T) input of a flip-flop 407.

The trigger input to flip-flop 405 is connected to the Q output offlip-flop 407, and the reset input of flip-flop 405 is connected to theoutput register (OPR) output of a 16-word by eight bit FIFO 408. Whenthe OPR output is at a logic 1 level, the output register is filled.Further, when the OPR output is at a logic zero level, the outputregister is empty. The Q of flip-flop 405 is applied to the transfer onparallel (TOP) input of FIFO 408.

The Q output of the flip-flop 407 is connected to its D input, and tothe T input of flip-flop 406. The reset input to flip-flop 406 isconnected to the OPR output of a 16-word by 8 bit FIFO 410. The Q outputof the flip-flop 406 is connected to the TOP input of FIFO 410, and tothe TOP input of a 16-word by 8 bit FIFO 411.

The load (LD) input to FIFO 408 is connected to a control line 412, andthe data input to the FIFO is connected to a data cable 408a leadingfrom data register 82 of FIG. 4. The parallel data output of FIFO 408 isconnected to a data cable 408b leading to cable 94. The LD input to FIFO410 is connected to a control line 413, and the data input to the FIFOis connected to a data cable 410a leading from data register 82. Theparallel output of the FIFO is applied through a data cable 410b tocable 94.

The LD input to FIFO 411 is connected to the output of an AND gate 414.The input register (IPR) output of the FIFO 411 is connected by way of acontrol line 415 to one input of an AND gate 416. The IPR output is at alogic one level when the input register is empty, and at a logic zerolevel when the input register is filled. The OPR output of FIFO 411 isapplied by way of a control line 411b to line 102b of FIG. 5.

A second input to gate 416 is connected to a third input to gate 403,and to a control line 417. A third input to gate 416 is connected to oneinput of gate 414, and to a control line 416a. The output of gate 416 isapplied to the T input of a flip-flop 418, the Q output of which isapplied to a control line 419 leading to the bus logic unit 128.

The D input to flip-flop 418 is connected to the output of an AND gate420, one input of which is connected to a control line 421. A secondinput to gate 420 is connected to a control line 422.

A second input to gate 414 is connected to control line 417, and a thirdinput to gate 414 is connected to a control line 423.

In a write operation wherein data is read from the main memory 12 ofFIG. 1 and written into a disk device serviced by the device adapter 14,a problem may arise during the transfer of a sequence of data bytes. Ifa request for additional data is not issued by the MPDC 10 when a databyte is received from the main memory unit 12, other system devices mayintercede to communicate with the memory unit. The MPDC thus would notbe able to maintain a transfer rate to the disk device. If a request fordata is made without regard for empty buffer locations, data stored inthe data register 82 of FIG. 4 may be lost before the full range of datato be transferred from main memory has been written upon the diskdevice. The logic system of FIG. 8 provides a means for obviating such aproblem.

In operation, when data is to be transferred from the main memory unit12 to the MPDC 10, firmware issues a logic 1 signal to control line 417.If the megabus 13 is clear for a data transfer, the bus logic unit 128of FIG. 5 issues a logic 1 signal to control line 422 to indicate thatthe megabus 13 is ready. Further, until the data transfer is completed,the control line 421 leading from the range and offset range controlunit 77 remains at a logic 1 level to indicate that the range count hasnot been exhausted. The output of gate 420, therefore, is at a logic 1level which is applied to the D input of the flip-flop 418.

Prior to any data being transferred to the MPDC 10, the FIFO's 408, 410and 411 are empty. The IPR output of FIFO 411 thus is at a logic 1 levelindicating that the input register is empty. Further, the bus logic unit128 supplies a logic 1 signal to control line 416a during a time periodwhen the MPDC 10 is not using the megabus 13 in servicing a bus cyclerequest. Thus, the output of the gate 416 is at a logic 1 level totoggle the flip-flop 418, thereby issuing a bus cycle request on line419 leading to the bus logic unit 128.

In generating a bus cycle request for output on the megabus 13, the buslogic unit 128 issues a logic 1 signal to control line 423 to indicatethat an MPDC 10 bus cycle request has been issued. The firmware controlsignal on control line 417 thereupon is applied through gate 414 to theload input of FIFO 411. A dummy byte thereby is loaded into the FIFOunder firmware control, and the IPR output of the FIFO transitions to alogic zero level. It is thus seen that each time a cycle request isgenerated at the Q output of flip-flop 418 to request additional datafrom main memory unit 12, a dummy byte is loaded into the FIFO 411.

When the main memory unit responds to the bus cycle request, the buslogic unit 128 issues a logic zero signal to control line 423 and alogic 1 signal to control lines 412 and 413. Data bytes supplied by themain memory unit 12 to the megabus 13 thereby are loaded from datacables 408a and 410a into FIFO 408 and FIFO 410, respectively. The buslogic unit 128 thereupon transitions the control line 416a to a logic 1level to indicate that the bus cycle request for data has becomeinactive. If the dummy data byte loaded into the FIFO 411 has droppedfrom the input register into the FIFO stack, the IPR output of the FIFOwill transition to a logic 1 level to again trigger the flip-flop 418 toissue another cycle request on control line 419.

The above-described process continues until the FIFOs 408 and 410 arefilled as indicated by the output register (OPR) outputs of the FIFOs.The FIFO 411 thus serves to indicate in advance that if a data word isloaded into the data FIFOs 408 and 410, the data word will pass into theFIFO stack before another data word can be requested of main memory unit12. More particularly, each time a data request is made to main memoryunit 12 a dummy byte is loaded into the FIFO 411. If the dummy byte haspassed into the FIFO stack before a next data request is made to mainmemory, then the time delays are such that it is known that the databytes in the FIFOs 408 and 410 shall pass into the respective FIFOstacks before additional data bytes are received from main memory.

When the FIFO units 408 and 410 are filled with data, the OPR outputs ofthe FIFO units are at a logic zero level indicating a filled condition.Further, the IPR output of FIFO 411 is at a logic zero level. The gate416 thus is disabled, and the generation of cycle requests on controlline 419 is terminated.

When the OPR output of FIFO 411 transitions to a logic 1 level toindicate that the data FIFOs 408 and 410 are filled, the hardwarecontrol unit 108 issues a strobe to the adapter logic unit 29. The logicunit 29 in turn issues a strobe to the device adapter 14 to indicatethat the data FIFOs may be emptied. The device adapter 14 thereuponissues a logic 1 hardware service request signal to control line 404,and the firmware in response thereto issues a hardware enable signal tocontrol line 402. The firmware further issues a logic 1 signal tocontrol line 401 to indicate that a write on disk operation has beeninitiated.

The flip-flop 407 is triggered by the output of gate 403, and togglesbetween set and reset conditions. For example, if the flip-flop is in aset condition, it resets upon being triggered. Further, if the flip-flopis in a reset condition, it sets upon being triggered. The Q and Qoutputs of the flip-flop thereby alternately trigger the flip-flops 405and 406 respectively. If the flip-flop 405 is triggered, the Q output ofthe flip-flop is applied to the TOP input of the FIFO 408. In responsethereto, the data byte in the output register of the FIFO is supplied todata cable 408b leading to the device adapter 14. When the outputregister is emptied, the OPR output of the FIFO 408 immediately resetsthe flip-flop 405. In like manner, when the flip-flop 406 is triggered,the Q output of the flip-flop supplies an unload signal to the FIFO 410.When the output register of the FIFO is emptied, the OPR output of theFIFO resets the flip-flop 406. It is apparent that the flip-flop 407 incombination with the flip-flops 405 and 406 alternately selects databytes from FIFO 408 and FIFO 410. The data bytes transmitted to thedevice adapter 14 thus are comprised of a left byte from FIFO 408 and aright byte from FIFO 410.

Each time the FIFO 410 is unloaded, the FIFO 411 also is unloaded. Assoon as the input register to the FIFO 411 is emptied, the IPR output ofthe FIFO transitions to a logic 1 level to generate a cycle requests asbefore described. As data bytes are loaded into the FIFOs 408 and 410,the FIFOs again are unloaded. Before a cycle request for a next databyte is requested from main memory unit 12, however, the input registerto the FIFO 411 must be emptied.

Two conditions may occur which may prevent the generation of a cyclerequest on control line 419 when the input register to FIFO 411 isempty. When the range count indicating the total number of data bytes tobe transferred from main memory unit 12 to the device adapter 14 isexhausted, line 421 transitions to a logic zero. Further, if anunsolicited bus request or other data occurs on the megabus 13 to causethe MPDC 10 to issue a NAK, the gate 420 is disabled. The Q output ofthe flip-flop 418 thus does not transition to a logic 1 level whentriggered, and no further cycle requests may be made.

FIG. 9

FIG. 9 is a timing diagram illustrating in graphic form the operation ofthe system of FIG. 8.

It is to be understood that the system disclosed herein is comprised ofdevices in intercommunication on an asynchronous bus. Thus, absolutetime values are not disclosed in the description of the timing diagramsof FIGS. 9-11. It is the order of occurrence rather than the absolutetime of occurrence which is of primary importance.

Referring to FIG. 9, a waveform 501 illustrates a signal issued byfirmware to place the MPDC 10 into a write mode, and a waveform 502illustrates a cycle request signal issued by the bus logic unit 128 ofFIG. 5 in response to firmware commands. A waveform 503 illustrates abus cycle request made by the MPDC 10 to the megabus 13, and a waveform504 illustrates a strobe issued by the bus logic unit 128 to set thecycle request logic signals of waveform 502 onto the megabus 13 asindicated by waveform 503. A waveform 505 illustrates a logic signalformed on the megabus 13 in response to the logic signals of waveforms503 and 504. A waveform 506 illustrates a waveform generated in the MPDC10 to indicate that the MPDC is busy. A waveform 507 illustrates a logicsignal issued by a slave to the megabus 13 in response to a bus requestissued by a master device. A waveform 508 illustrates an acknowledgementlogic signal issued by the MPDC 10 to the megabus 13 in response to asecond-half bus cycle signal from the main memory unit 12 as illustratedby a waveform 509. A waveform 510 illustrates the load signal issued bythe gate 414 to the FIFO 411 of FIG. 8, and a waveform 511 illustratesthe logical inverse of the input register output of the FIFO 411. Awaveform 512 illustrates the logic signal issued by the output registerof the FIFO 411 when the data FIFOs 408 and 410 are filled.

In the mnemonics used to describe the waveforms 501-512 in FIG. 9, aplus sign (+) indicates that the condition signified by the mnemonicoccurs when the associated waveform is at a logic 1 level. A negativesign (-) indicates that the designated condition occurs when thewaveform is at a logic zero level.

When data is to be written from main memory unit 12 of FIG. 1 to a diskdevice serviced by the device adapter 14, firmware transitions thecontrol line 417 of FIG. 8 to a logic 1 level as indicated at 501a ofwaveform 501. Since the bus cycle is not active as indicated at 506a ofwaveform 506, the MPDC 10 is not engaged in servicing a previous buscycle request. Thus the control line 416a is at a logic 1 level, and alogic 1 signal issued by the input register FIFO 411 as illustrated at511a of FIG. 11 is applied through the gate 416 to trigger the flip-flop418. The Q output of flip-flop 418 thereupon transitions to a logic onelevel as illustrated at 502a. The cycle request 502a thereby is placedonto the megabus 13 as control line 419. When a cycle of the megabus 13is available, the bus logic unit 128 of FIG. 5 will issue a logic 1pulse 504a to place the cycle request 502a onto the megabus 13 asillustrated by the logic 1 pulse 503a. The signal appearing on themegabus 13 in response to the pulses 503a and 504a is illustrated by alogic 1 pulse 505a of waveform 505.

The bus logic unit 128 issues a logic 1 pulse 506b concurrently withpulse 504a to indicate that the bus cycle is active, i.e., the MPDC 10is busy. In response thereto, the output of gate 414 transitions to alogic 1 level as illustrated by a logic 1 pulse 510a to load a dummybyte into the FIFO 411. Upon receiving the bus cycle request from theMPDC 10, the main memory unit 12 acknowledges its acceptance of therequest by issuing a logic 1 pulse 507a of waveform 507.

When the dummy byte is loaded into the FIFO 411, the waveform 511transitions to a logic zero level as indicated at 511a. Since gate 416will be disabled during the time period that waveform 511 remains at alogic zero level, no further bus cycle requests may be made until thewaveform again transitions to a logic 1 level.

When the main memory unit 12 has retrieved a requested data word andplaced it on the megabus 13, the memory unit issues a logic 1 pulse 509ato indicate that the data is available. Further, the memory unit issuesa logic 1 pulse 505b. Upon receiving the pulses 505b and 509a, the buslogic unit 128 issues an acknowledgement logic 1 pulse 508a whichappears on the megabus 13 as logic 1 pulse 507b. Upon receiving thepulse 507b, the main memory unit releases the megabus 13 to accommodateanother bus cycle request. Upon issuing the pulse 508a, the MPDC 10 isno longer in a bus cycle active state as indicated at 506c. Since theoutput of the input register of the FIFO 411 is again empty as indicatedat 511b, a logic 1 pulse 502b is supplied at the Q output of flip-flop418 to initiate a next bus cycle request operation.

FIG. 10

FIG. 10 is a timing diagram illustrating the operation of the system ofFIGS. 4-8 during a data transfer from a disk device to megabus 13.

A waveform 600 illustrates the hardware data service request signalissued by the device adapter 14 to control line 110 of FIG. 4, and awaveform 601 illustrates the hardware enable signal issued by firmwarein response to the waveform 600. A waveform 602 illustrates a hardwaredata service enable signal which is a logical AND of waveforms 600 and601. Waveform 602 illustrates the enable signal applied by firmware tothe EN2 enable input of range clock logic unit 316 of FIG. 7 duringdiagnostic tests.

A waveform 603 illustrates the output of range clock logic unit 316 inresponse to the enable signal illustrated by waveform 602. A waveform604 illustrates the output of gate 403 of FIG. 8, and the output of theadapter logic unit 29 of FIG. 4. A waveform 605 illustrates the inverseto the Q output of flip-flop 407 of FIG. 8.

Waveforms 606 and 607 each are formed from waveforms 604 and 605, andindicate the output states of the flip-flop 407. A waveform 608illustrates the bus cycle request signals issued at the Q output offlip-flop 418 of FIG. 8, and a waveform 609 illustrates the pulse pairsgenerated by the address clock logic unit 304 each time a cycle requestis made as illustrated by waveform 608.

When data is to be read from a disk device, the device adapter 14 ofFIG. 4 issues a logic 1 pulse 600a to control line 110 to indicate thata data byte is available for transfer to the MPDC 10. In responsethereto, the firmware control system of FIG. 6 issues an enable hardwarepulse 601a to the control line 109 of FIG. 4 leading to the hardwarecontrol unit 108. As the data byte is transferred from the deviceadapter 14 to the MPDC 10, the timing signal illustrated by waveform 602is applied to the range clock logic unit 316 of FIG. 7. In responsethereto, the offset range counters 308 and 309 are decremented until theoffset range count is exhausted. The range counters 306 and 307thereafter are decremented as illustrated by the logic 1 pulses ofwaveform 603.

Each time data bytes are transferred from the device adapter 14 to theMPDC 10, the output of gate 403 as illustrated by the waveform 604triggers the flip-flop 407. When the Q output of flip-flop 407 is at alogic 1 level, flip-flop 405 is triggered to load a left byte in busdata register 100 for transfer to the megabus 13. This condition isillustrated by the logic 1 levels of waveform 605 and waveform 607. Whenthe Q output of the flip-flop 407 transitions to a logic 1 level, theflip-flop 406 is triggered to load a right byte in register 100 fortransfer to the megabus 13. This condition is illustrated by the logiczero levels of waveform 605 and the logic 1 levels of waveform 606.

When a data word comprising a left and a right data byte have beenformed in the register 100, the bus logic unit 128 under firmwarecontrol issues a bus cycle active signal to control line 416a of FIG. 8to trigger the flip-flop 418. A bus cycle request thereby is generatedas illustrated by the logic 1 levels of waveform 608. Each time a busycycle request is generated, the bus logic unit 128 enables the addressclock logic unit 304 to issue logic 1 pulse pairs as illustrated bywaveform 609. The main memory address stored in the bus address counters300, 302 and 303 thereupon is incremented by two.

Should an interim condition arise wherein data is not available fortransfer to the MPDC 10 before the range count has been exhausted, thedevice adapter issues an interrupt to line 125 of FIG. 4 to returncontrol from the system hardware system to the firmware. In that event,the enable hardware signal of waveform 601 transitions to a logic zerolevel as indicated at 601b. No further MPDC activity occurs until thedevice adapter 14 indicates that data again is available for transfer byissuing a logic 1 pulse 600b to line 110 of FIG. 4. The data transferthereafter continues as before described until the range counter isexhausted.

FIG. 11

FIG. 11 is a timing diagram illustrating the operation of the system ofFIGS. 4-8 during a write operation.

A waveform 700 illustrates the hardware data service request signalissued by the device adapter 14 to the control line 110 of FIG. 4, and awaveform 701 illustrates a strobe signal issued by the adapter logicunit 29 to control lines 29a and 118b of FIG. 4. A waveform 702illustrates the output of gate 403 of FIG. 8, and a waveform 703illustrates the logic inverse of the Q output of the flip-flop 407. Awaveform 704 illustrates the logic inverse of the Q of flip-flop 405,and a waveform 705 illustrates the output register (OPR) output of FIFO408.

A waveform 706 illustrates the logic inverse of the Q output offlip-flop 406, and a waveform 707 illustrates the OPR output offlip-flop 410. A waveform 708 illustrates the OPR output of FIFO 411,and a waveform 709 illustrates the logic inverse of the IPR output ofFIFO 411. A waveform 710 illustrates the Q output of flip-flop 418, anda waveform 711 illustrates a bus cycle request signal generated by thebus logic unit 128 in response to the waveform 710.

A waveform 712 illustrates a bus cycle active signal placing the MPDC 10in a busy state in response to the bus cycle request pulses of waveform711. A waveform 713 illustrates a data cycle signal issued by the buslogic unit 128 to indicate a time period in which the main memory unit12 must acknowledge a data request from the MPDC 10. A waveform 714illustrates the bus request and acknowledgement pulses occurring on themegabus 13 as a result of the handshaking between the MPDC and the mainmemory. A waveform 715 illustrates the bus acknowledgement pulses issuedby a slave system device in response to a bus request from a mastersystem device, and a waveform 716 illustrates MPDC acknowledgementpulses which are reflected in the pulses of waveform 715. A waveform 717and a waveform 718 respectively illustrate address increment pulses andrange decrement pulses generated during the transfer of data from mainmemory unit 12 to the device adapter 14.

Prior to the transfer of data from main memory, the device adapter 14positions the write heads of a disk device at a designated record. Afterthe disk device is prepared for a write operation, the adapter 14 issuesa hardware service request signal as illustrated by pulse 700a to thecontrol line 110. The bus logic unit 128 thereupon requests data fromthe main memory unit 12. The main memory unit 12 in response thereto,supplies data to the data register 82 of FIG. 4. Under control of thedata control unit 113, the data is transferred from data register 82into the data FIFOs 408 and 410. When the data FIFOs are filled, thehardware control unit 108 signals the adapter logic unit 29. The logicunit 29 in turn issues a strobe pulse 701a to the device adapter 14 toindicate that a data byte is being transferred. Concurrently, gate 403of FIG. 8 issues a pulse 702a to select a data byte from one of theFIFOs 408 and 410 for transfer to the device adapter 14. In response tothe gate 403 output, flip-flop 407 of FIG. 8 issues a pulse 703a totrigger the flip-flop 405. Flip-flop 405 in turn issues a pulse 704a toselect a data byte from the FIFO 408.

When the data byte is taken from the output register of the FIFO 408,the OPR output of the FIFO transitions to a logic zero level asindicated at 705a. The OPR output further resets the FIFO 405 asindicated at 704b of waveform 704. When the data byte has been taken bythe device adapter 14, the adapter issues a second hardware data servicerequest pulse 700b. In response thereto, the adapter logic 29 pulse 701band the gate 403 pulse 702b are generated as before described. Upon theoccurrence of pulse 702b, the Q output of the flip-flop 407 triggers theflip-flop 406 as indicated at 703b of waveform 703. The Q output offlip-flop 406 thereupon issues a logic 1 pulse 706a to unload the outputregister of the FIFO 410. When the data byte is transferred out of theoutput register, the OPR output of the FIFO 410 transitions to a logiczero as indicated at 707a of waveform 707. In response to the logictransition of the OPR output, the flip-flop 406 is reset as indicated at706b.

As before described, the FIFO 411 is unloaded at the same time the FIFO410 is unloaded. Thus, when the OPR output of FIFO 410 transitions to alogic zero, the OPR output of FIFO 411 also transitions to a logic zeroas indicated at 708a of waveform 708. When an additional dummy byteenters the output register of FIFO 411, the OPR output transitions to alogic 1 as indicated at 708b. In addition, the input register output IPRchanges state as indicated at 709a. A bus cycle request on control line419 thereby is initiated as indicated by logic one pulse 710a. Inresponse to pulse 710a, the bus logic unit 128 of FIG. 5 issues a strobepulse 713a to place the cycle request pulse 710a onto the megabus 13 asindicated by pulse 711a. Upon the occurrence of the strobe 713a and thepulse 711a, a pulse 714a is carried by the megabus 13 to the main memoryunit 12.

When the cycle request pulse 710a is generated, the bus logic unit 128places the MPDC 10 in a busy state as indicated by the logic 1 pulse712a. During the time period of the pulse 712a, the MPDC 10 issues adata request to the main memory unit 12 as indicated by pulse 714a andawaits a response.

If the memory unit 12 accepts the bus cycle request and the main memoryaddress supplied by MPDC 10, the main memory unit issues a pulse 715a.In response thereto, the bus logic unit 128 of FIG. 5 transitions thebus cycle request signal illustrated by waveform 711 to a logic zerolevel as indicated at 711b. During a time period not exceeding thatindicated by the logic 1 pulse 712a, the main memory unit retrieves thecontents at the indicated main memory address and supplies the data tothe megabus 13. In addition, the main memory unit issues a pulse 714b tonotify the MPDC 10 that data at the indicated main memory address isforthcoming. In response thereto, the bus logic unit 128 issues a strobe716a to place an acknowledgement pulse 715b on the megabus 13.Concurrently therewith, the bus logic unit removes the MPDC 10 from thebusy state as indicated by the logic zero level 712b of waveform 712.

The above-described process is repeated until the total number of databytes indicated by the range count has been transferred from the mainmemory unit 12 to the device adapter 14.

During the data transfer process, the bus address counters 300, 302 and303 are incremented and the range counters 306-309 are decremented. Moreparticularly, the address counters are incremented twice as indicated bypulses 717a and 717b each time a data request is made to the main memoryunit 12 as indicated by pulse 715a. Further, the range counters aredecremented each time a data byte is requested by the MPDC 10 from themain memory unit 12. One decrement command as illustrated by pulse 718ais issued when a request 710a for a data word is issued. A seconddecrement command as illustrated by pulse 718b is issued by the mainmemory unit 12.

In accordance with the invention, a data transfer accounting system isprovided which is responsive to both hardware and firmware control. Moreparticularly, address counters and range counters are connected in amanner to form a serial data path. Firmware thereby may load thecounters with address and range parameters prior to a data transfer withminimal interaction. Counter control is thereafter transferred tohardware to accommodate a data transfer rate higher than that possiblewith firmware control.

Having described the invention in connection with certain specificembodiments thereof, it is to be understood that further modificationsmay now suggest themselves to those skilled in the art, and it isintended to cover such modifications as fall within the scope of theappended claims.

What is claimed is:
 1. A data transfer control system in a peripheralcontrol unit having a scratchpad memory unit and a hardware controlmeans, said control system having architecture accommodating both theloading of memory address, range and offset range parameters in a serialstream, and the dynamic amending of said parameters during a datatransfer between a disk device and a main memory unit of a dataprocessing system wherein said peripheral control unit and said mainmemory unit are electrically coupled by an asynchronous communicationbus, which comprises:a. a memory address counter responsive to saidhardware control means for dynamically updating memory addressinformation to said bus during a data transfer; b. a range counterelectrically connected to said memory address counter to form a serialdata path and responsive to said hardware control means for indicatingthe completion of a data transfer to said hardware control means; c. anoffset range counter electrically connected to said range counter inextension of said serial data path and responsive to said hardwarecontrol means for dynamically indicating to said hardware control meansthe occurrence of a first data byte in an information stream to betransferred; and d. firmware control means responsive to said hardwarecontrol means between data transfers for circulating a serial stream ofsaid parameters through said scratchpad memory unit, said memory addresscounter, said range counter and said offset range counter, therebystoring control information in said scratchpad memory unit forreinitiating a data transfer in the event of a data transfer error.
 2. Adata transfer control system in a peripheral control unit of a dataprocessing system having a main memory unit and said peripheral controlunit electrically coupled to an asynchronous communication bus, saidperipheral control unit in electrical communication with a disk deviceand including a scratchpad memory unit and a hardware control means,which comprises:a. a clock means for autonomously supplying logiccontrol signals to said control system at a clock rate; b. first logicmeans responsive to said clock means and said hardware control means forproviding address control signals; c. second logic means responsive tosaid clock means and said hardware control means for providing range andoffset range control signals; d. first counter means responsive to saidaddress control signals for dynamically updating memory address signalsto said main memory unit during a data transfer; e. second counter meansresponsive to said range control signals and in electrical communicationwith said first counter means to form a serial data path for indicatingto said hardware control means the termination of said data transfer; f.third counter means responsive to said offset range control signals andin electrical communication with said second counter means in extensionof said serial data path for dynamically indicating to said hardwarecontrol means the occurrence of a first data byte in an informationstream to be transferred; and g. firmware control means in electricalcommunication with said hardware control means for circulating a datastream through said scratchpad memory unit and along said serial path toload said first, said second and said third counter means with memoryaddress, range count and offset range count parameters, respectively,and to store said parameters between data transfers in said scratchpadmemory unit to provide control signals for retransferring data in theevent of a data transfer error.
 3. A counter control system in aperipheral control unit having a scratchpad memory unit foraccommodating high data transfer rates between a disk control unit and amain memory unit of a data processing system including a centralprocessing unit, said main memory unit and said peripheral control unitelectrically coupled to an asynchronous communication bus, whichcomprises:a. hardware control means responsive to said disk control unitand to control information supplied by said central processing unit forcontrolling the transfer of data through said peripheral control unit;b. first counter means in electrical communication with said bus andresponsive to said hardware control means during data transfers forproviding memory addresses to said bus; c. second counter means inserial electrical connection with said first counter means andresponsive to said hardware control means during data transfers forindicating the end of a data transfer to said hardware control means; d.third counter means in serial connection with said second counter meansand responsive to said hardware control means during data transfers forindicating to said hardware control means the occurrence of a first databyte in an information stream to be transferred; and e. firmware controlmeans responsive to said hardware control means for issuing loadcommands to said first, said second, and said third counter meansbetween data transfers to serially shift information from saidscratchpad memory through said counter control system to said scratchpadmemory, thereby providing control information to reinitiate a datatransfer in the event of a data transfer error.
 4. A counter controlsystem structure in a peripheral controller in electrical communicationwith a main memory and a central processing unit of a data processingsystem, said peripheral controller having a scratchpad memory forreceiving data transfer control information from said main memory undercontrol of said central processing unit, and a hardware control systemfor controlling the transfer of data into and out of said peripheralcontroller in response to said control information, said counter controlsystem comprising:(a) firmware control means responsive to said hardwarecontrol system for effecting the transfer of said control informationbetween said counter control system and said scratchpad memory; (b)first counter means responsive to a command issued from said firmwarecontrol means during time periods between data transfers foraccommodating a serial transfer from said scratchpad memory of saidcontrol information including offset range count parameters indicatingthe commencement of a data transfer, range count parameters indicatingthe termination of a data transfer and memory address parametersindicating memory locations in said main memory for use by said hardwarecontrol system during data transfers; (c) second counter meanselectrically connected to said first counter means to form a serial datapath therewith, and responsive to said command for accommodating aserial transfer of said offset range count, range count and memoryaddress parameters from said first counter means to said second countermeans; and (d) third counter means electrically connected to said secondcounter means in extension of said serial data path, and in electricalcommunication with said scratchpad memory, and responsive to saidcommand for accommodating a serial shift of said offset range count,range count and memory address parameters from said second counter meansto said third counter means, and from said third counter means to saidscratchpad memory, thereby completing a serial transfer loop betweensaid scratchpad memory and said counter control system for accommodatingthe loading of said counter control system with said control informationto initiate a data transfer, and with immediately preceding countinformation of said counter control system to accommodate thecontinuation of a data transfer in the event of a data transfer error,without substantially affecting data transfer rates.